Global Configuration

The Configuration page lets you configure Live Platform global settings.

Do the following:
1. Open the Server Configuration page (System > Administration > Configuration).

2. Perform configuration according to the table below.

Parameter

Description

Live Platform Hostname FQDN

FQDN of the Live Platform Server.

For Live Platform to connect to Microsoft Teams, an FQDN (e.g., Enterprise.com) rather than a hostname (e.g., prod-Live-Platform) must be used.

Description

Description field that is forwarded in Alarm Info

Device and External Applications Communication

From the 'Device and External Applications Communication' drop-down list, select one of the following values:

FQDN Based: OVOC Server FQDN Hostname configured in the OVOC Hostname field is used to secure the device communication. Specify the hostname in the format "OVOC-Hostname.com".
IP-Based: OVOC Server IP address is used to secure the device communication.
External applications includes the Device Manager, Routing Manager and UCaaS.
For Live Platform/OVOC Non-SaaS deployments: If this parameter is set to "FQDN Based" and the Cloud Architecture feature is enabled in the OVOC Server Manager, then the connected devices cannot be managed for this OVOC instance.

FQDN Support for Auto-Detection

FQDN of the Live Platform server. This parameter is used for Auto Detection when connecting devices to the network. When enabled, you can add devices directly to the associated tenant in a single action. See Connecting Devices Automatically.

Service Availability

Enables the Service Availability feature for monitoring SBC devices configured in a cluster (see Service Availability).

Privacy Mode

When the “Privacy” mode is enabled, the following call data is affected for operators with “operator” and “monitor” levels:

Gateway and SBC phone numbers
Existing User/URI reports or schedulers and no new data generated
Existing user tables and statistics and no new data is generated
User/URI reports and their respective schedulers
Calls/SIP ladder (new data is not retrieved)
For Teams call:
Partial masking for Phone CDRs
Full masking for CDR URIs
Full masking for MDRs
Full masking for Conference CDRs

Masked Digits Number

The number of digits that will be masked from the phone number when the 'Privacy Mode' parameter is enabled. This setting defines the global number of digits that will be masked from the phone number. For information about configuring 'Masked Digits Number' per tenant, see Adding Service Provider Tenants.

By default, Live Platform conceals the last four digits from users' phone numbers. The configuration can be changed on-the-fly if necessary.

If both this global parameter and the per-tenant parameter are defined, the one with the higher number of masked digits configured takes priority.

If you're operating with multiple tenants, take the highest number of masked digits configured and apply it to your tenants calls. Example: Tenant A is configured with four masked digits while Tenant B is configured with six; the operator assigned to both tenants will see six digits masked in both tenants' users' calls.

Masking rules apply to both Calls List page and to the Call Details screen.

Device Manager FQDN

FQDN of the Live Platform Server. This parameter is used for Auto Detection when connecting phones to the network. When enabled, you can add phones directly to the associated tenant in a single action (instead of the devices firstly being added to the default Auto Detection region) and then moved to the tenant.

User Experience Data Monitoring

This version includes an integrated app for learning on AudioCodes Live portal is used, which pages are visited, time on each page, and typical user flows.

OVOC’s app is GDPR and CCPA compliant. It complies with the following GDPR policy privacy instructions:

https://matomo.org/privacy/
https://matomo.org/gdpr-analytics/

Data is collected and analyzed based on customer reports sent to the app server located in the cloud. The following OVOC application data is monitored:

Page Title
Page URL
Buttons clicked and Options selected in Drop-down menus
Filter settings
Controls changes (for example, in the Alarms page, if table columns were resized, filter / summary panels closed, graphs opened in large view)
Forms Opening and Editing

System Logo

Option to upload System or Service Provider logo.

Internal Mail Server from Address

If your enterprise uses Live Platform's internal email server for Alarms Forwarding, use this parameter to configure the internal mail server’s 'From Address'. For example, if you configure adelev@TrunkOperator.com for this parameter and you configure 'Adele Vance' for the parameter following in this table ('Internal Mail Server Real Name'), then all alarms forwarded from Live Platform by email from rules configured with 'Use Internal Mail Server' will be from address: adelev@TrunkOperator.com

This option can also be configured per tenant (see Adding Service Provider Tenants).

Internal Mail Server Real Name

The corresponding name of the System Administrator configured for the 'Internal Mail Server from Address' above.

This option can also be configured per tenant (see Adding Service Provider Tenants).

Graphical user interface, text, application, email

Description automatically generated

Graphical user interface, text, application, email

Description automatically generated